Skip to content

fix: isolate inline OAuth credential caches - #30

Closed
ryanduguid wants to merge 1 commit into
XeroAPI:mainfrom
ryanduguid:fix/oauth-cache-key-lifecycle
Closed

fix: isolate inline OAuth credential caches#30
ryanduguid wants to merge 1 commit into
XeroAPI:mainfrom
ryanduguid:fix/oauth-cache-key-lifecycle

Conversation

@ryanduguid

Copy link
Copy Markdown

Summary

  • scope inline OAuth token-cache entries to their client ID instead of sharing _inline
  • add logout --client-id and remove the unsafe legacy inline entry during inline logout
  • remove cached tokens when profiles are removed or force-replaced
  • document and test the inline credential lifecycle

Pre-existing _inline entries cannot be safely associated with a client ID, so inline users are deliberately required to authenticate again after this change. Named/default profile behavior is unchanged.

Validation

  • npm test (10 files, 143 tests)
  • npm run build
  • npx tsc --noEmit
  • git diff --check HEAD^ HEAD

@ryanduguid

Copy link
Copy Markdown
Author

Closing this one to cut the review load I created here.

I opened a large batch against this repository on 6 August. That was more than any maintainer could reasonably work through, and it was the wrong way to contribute. I have kept open the few changes with the clearest user impact and closed the rest, including this one.

The branch stays on my fork and the change still applies, so if this one is useful, say so and I will reopen it.

@ryanduguid ryanduguid closed this Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants